X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81668.883182C2@onstor-exch02.onstor.net>; Wed, 24 Oct 2007 11:05:59 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Rocket98 item - bobcat to Cougar migration
Date: Wed, 24 Oct 2007 11:05:59 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E062AD5BD@onstor-exch02.onstor.net>
In-Reply-To: <471E11A3.1020805@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rocket98 item - bobcat to Cougar migration
Thread-Index: AcgViH9AYq4P+/ORRtyJo79Q28yObwA3415g
References: <471E11A3.1020805@onstor.com>
From: "Jonathan Goldick" <jonathan.goldick@onstor.com>
To: "Narain Ramadass" <narain.ramadass@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>

In the assumptions you should include that the IP networking is cabled
the same ways as for the Bobcat.  If you are going from a 2220 to a
Cougar you must ensure that the two cables are connected to the first
Cougar IP ports and in the same order as before.

You need to handle migration of MAC addresses so that SAN zoning will
continue to work.  The procedure should be similar to when we swap
Bobcat(s).

-----Original Message-----
From: Narain Ramadass=20
Sent: Tuesday, October 23, 2007 8:22 AM
To: dl-Design Review
Subject: Rocket98 item - bobcat to Cougar migration

All,

Please find attached a document detailing our understanding of the=20
above-mentioned item in the Rocket98 plan.

Comments (particularly additions to the scope, modifications to the=20
workflow) would be greatly appreciated.

Thanx,
Narain.

